package rim;

import javax.persistence.ManyToOne;

import datatypes.r2.basic.CD;
import datatypes.r2.basic.CS;
import datatypes.r2.flavors.BN;
import datatypes.r2.flavors.INT_NONNEG;
import datatypes.r2.flavors.PQ_TIME;
import datatypes.r2.flavors.ST_SIMPLE;
import datatypes.r2.foundation.BL;
import datatypes.r2.foundation.DSET;
import datatypes.r2.quantities.REAL;

/**
 * Definition of ActRelationship:
 * 
 * A directed association between a source Act and a target Act.
 * 
 * 源法和目标法之间的直接关联。
 * 
 * 
 * UsageNotes:
 * 
 * The ActRelationship class is used to construct systems of acts to represent
 * complex observations, action plans, and to represent clinical reasoning or
 * judgments about action relationships. Prior actions can be linked as the
 * reasons for more recent actions. Supporting evidence can be linked with
 * current clinical hypotheses. Problem lists and other networks of related
 * judgments about clinical events are represented by the ActRelationship link.
 * 
 * Every ActRelationship instance is like an arrow with a point (headed to the
 * target) and a butt (coming from the source). The functions that source and
 * target Acts play in that association are defined for each ActRelationship
 * type differently. For instance, in a composition relationship, the source is
 * the composite and the targets are the components. In a reason-relationship
 * the source is any Act and the target is the reason or indication for the
 * source-Act.
 * 
 * The relationships associated with an Act are considered properties of the
 * source act object. This means that the author of an Act-instance is also
 * considered the author of all of the act relationships that have this Act as
 * their source, (though not necessarily of the target Acts of those
 * relationships). There are no exceptions to this rule.
 * 
 * The meaning and purpose of an ActRelationship is specified in the
 * ActRelationship.typeCode attribute.
 * 
 * ActRelationship类用于建设行为的系统来表示复杂的意见，行动计划，并表示有关行动关系的临床推理或判断。之前的行动可以联系最近的行动的原因。
 * 可以与目前临床上假设的支持证据。问题清单和其他有关临床事件的相关判断网络的代表由ActRelationship链接。
 * 
 * 每ActRelationship实例，就像是一个一个点（朝向目标）和屁股（源）的箭头。不同定义每个ActRelationship类型的源和目标的行为，
 * 在该协会中发挥的功能。例如，在组成的关系，源是复合目标的组成部分。在原因关系的来源是任何法令和目标是什么原因或源法“的迹象。
 * 
 * 与法案相关的关系被认为是来源的行为对象的属性。这意味着，笔者的一项法令，实例​​也认为此法有其来源的行为关系作者（虽然不一定是目标，这些关系的行为）。
 * 有没有此规则的例外。
 * 
 * 意义和目的的ActRelationship指定在ActRelationship.typeCode属性。
 * 
 * 
 * Examples:
 * 
 * has component, fulfills, has reason.
 * 
 * 1) An electrolyte observation panel may have sodium, potassium, pH, and
 * bicarbonate observations as components. The composite electrolyte panel would
 * then have 4 outbound ActRelationships of type "has component," which would be
 * inbound to their target sodium, potassium, pH, and bicarbonate observations.
 * 
 * 2) The electrolyte panel event has been performed in fulfillment of an
 * observation order. The electrolyte panel event has an outbound
 * ActRelationship of type "fulfills" with the order as target.
 * 
 * 3) A Procedure "cholecystectomy" may be performed for the reason of an
 * Observation of "cholelithiasis." The procedure has an outbound
 * ActRelationship of type "has reason," which would be inbound to the
 * cholelithiasis observation.
 * 
 * 组件，满足，有原因。
 * 
 * 1）电解质观察面板可能有钠，钾，pH值，碳酸氢盐作为组件意见。复合电解质面板将有4型的出境ActRelationships“有分量”，
 * 这将是进入他们的目标钠，钾，pH值，和碳酸氢盐观测。
 * 
 * 2）电解质面板事件已经履行的观察顺序进行。电解液面板事件有出境ActRelationship型“满足”为目标的顺序。
 * 
 * 3）一个过程“胆囊切除术”，可观察的原因，“胆石症”。过程有一个类型的出境ActRelationship“有原因，”这将是进入胆石症观察。
 * 
 * 
 * @author Obama
 * 
 */
public class ActRelationship extends InfrastructureRoot {

	private static final long serialVersionUID = 1L;

	/**
	 * Definition: The meaning and purpose of the ActRelationship instance.
	 * 
	 * 的意义和目的的ActRelationship实例。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * The ActRelationship class is used to construct a variety of semantic
	 * structures, including panels, action plans, and representations of
	 * clinical reasoning or judgments. Prior actions can be linked as the
	 * reasons for more recent actions. Supporting evidence can be linked with
	 * current clinical hypotheses. Problem lists and other networks of related
	 * judgments about clinical events are represented by the ActRelationship
	 * link. The typeCode implies specific constraints on what kinds of Act
	 * objects can be related and in what way.
	 * 
	 * The types of act relationships fall under 6 categories:
	 * 
	 * 1) Composition, with composite (source) and component (target). One of
	 * the most commonly used ActRelationship types is "has component" to
	 * describe the composition and de-composition of Acts. The relationship
	 * type allows specifying detail of Acts to varying degrees.
	 * 
	 * The composition relationship can group actions into "batteries," e.g.,
	 * LYTES, CHEM12, or CBC, where multiple routine laboratory tests are
	 * ordered as a group. Some groupings, such as CHEM12, may be defined by a
	 * specific implementation; others, such as blood pressure, seem to
	 * naturally consist of systolic and diastolic pressure.
	 * 
	 * With the composition relationship, the detail of Acts can be revealed to
	 * different levels for different purposes without the structure of the Act
	 * hierarchy needing to be rearranged. This allows supporting multiple
	 * viewpoints on the same business processes. For instance, a billing
	 * viewpoint of a laboratory test battery may be as a single billable act. A
	 * clinician's view of the same laboratory test battery is as a set of
	 * individual observations, where the ordering among the observations is
	 * irrelevant. The laboratory's view of this act will be more detailed,
	 * including action plan steps that are never reported to the clinician
	 * (e.g., centrifugation, decantation, aliquoting, running certain machines,
	 * etc.). The laboratory's viewpoint warrants a thorough specification of
	 * action plans (that can be automated). During this specification, more and
	 * more nested sub-activities will be defined. Still, the source Act is the
	 * same, with varying degrees of detail uncovered in the de-composition
	 * relationship.
	 * 
	 * 2) Sequel, which includes follow-up, fulfillment, instantiation,
	 * replacement, transformation, etc., for which source and target are Acts
	 * of essentially the same kind but with variances in mood, and where the
	 * target exists before the source.
	 * 
	 * 3) Pre-condition, trigger, reason, contraindication, with the conditioned
	 * Act ("give aspirin") at the source and the condition or reason Act
	 * ("if fever above threshold") at the target.
	 * 
	 * 4) Post-condition, outcome, goal and risk, with the Act at the source
	 * having the outcome or goal at the target.
	 * 
	 * 5) Workflow. The composition and sequence relationships can be arranged
	 * in a sequence to form temporal and conditional (non-temporal) action
	 * plans (e.g., care plan, critical path, clinical trials protocols, drug
	 * treatment protocols). There is a group of attributes in both Act and
	 * ActRelationship called the "workflow Control suite of attributes" that
	 * allow the detailed specification of executable action plans. These
	 * attributes are
	 * 
	 * Act.repeatNumber
	 * 
	 * Act.interrubtibleInd
	 * 
	 * ActRelationship.sequenceNumber
	 * 
	 * ActRelationship.pauseQuantity
	 * 
	 * ActRelationship.checkpointCode
	 * 
	 * ActRelationship.splitCode
	 * 
	 * ActRelationship.joinCode
	 * 
	 * ActRelationship.sequenceNumber arranges the components of an Act as a
	 * sequence or as concurrent collections of components, expressing logical
	 * branches as well as parallel tasks (tasks carried out at the same time).
	 * The ActRelationship attributes splitCode and joinCode control how
	 * branches are selected or executable in parallel.
	 * 
	 * Act.activityTime and ActRelationship.pauseQuantity allow one to
	 * explicitly time an action plan. Act.repeatNumber allows specifying act to
	 * repeat (loop), while Act.interruptibleInd determines whether an Act can
	 * be interrupted by related Acts.
	 * 
	 * The ActRelationship type has-precondition allows plan steps to be
	 * conditional on the status or outcome of previous actions. The
	 * ActRelationship.checkpointCode specifies when pre-conditions of acts are
	 * tested during the flow of control. See the individual attribute entries
	 * in this model for more information.
	 * 
	 * The composition ActRelationship allows these constructs to be organized
	 * in nests and layers to fully support workflow management. This nesting
	 * and the workflow control attributes are designed in analogy to a
	 * block-structured programming language with support for concurrency (fork,
	 * join, interrupts), and without "goto" statements. All workflow plans are
	 * established through sequencing components (steps) in a composite act
	 * (block) consistent with structured programming principles.
	 * 
	 * 6.) A host of functional relationships including support, cause,
	 * derivation, etc. generalized under the notion of "pertinence."
	 * 
	 * ActRelationship类是用于构建一个语义结构的品种，包括面板，行动计划，以及临床推理或判断的申述。之前的行动可以联系最近的行动的原因。
	 * 可以与目前临床上假设的支持证据
	 * 。问题清单和其他有关临床事件的相关判断网络的代表由ActRelationship链接。的TypeCode意味着，可与各种法令对象
	 * ，并以何种方式的具体限制。
	 * 
	 * 属于6类行为的关系类型：
	 * 
	 * 1）组成，复合材料（源）和组件（目标）。最常用的ActRelationship类型之一是“有分量”来形容的组成和德行为组成。关系类型允许指定的行为
	 * ，不同程度的细节。
	 * 
	 * 组成关系可以组合成“电池”，例如，LYTES，CHEM12或多个常规化验血常规，为一组排列的行动。如CHEM12一些集团，可以定义一个具体的实施;
	 * 其他如血压，似乎自然包括收缩压和舒张压。
	 * 
	 * 与组成的关系，详细的行为，可以发现不同用途的不同层次，而不需要重新安排该法层次结构。这使得相同的业务流程，支持多种观点。例如，
	 * 一个实验室测试电池计费的观点可能是作为一个单一的计费行为
	 * 。一个医生的观点相同的实验室测试电池是一套个人的意见，其中的意见之间的顺序是无关紧要的。实验室的这一行为的看法会更详细
	 * ，包括行动计划，从未向医生（例如
	 * ，离心，倾析，aliquoting，运行某些机等）的步骤。实验室的观点值得深入规范的行动计划（可自动）。在本规范中，
	 * 越来越多的嵌套的子活动，将被定义。尽管如此，源法是一样的，在德组成的关系发现不同的详细程度。
	 * 
	 * 2）续集，其中包括后续行动，履行，实例，更换，改造等，源和目标基本上是同类的行为，但与情绪的差异，并在目标前源存在。
	 * 
	 * 3）前置条件，触发，因此，禁忌，与空调法“（”给予阿司匹林“），从源头上和条件或原因法”（“如果发烧高于阈值”）的目标。
	 * 
	 * 4）后置条件，结果，目标和风险，与法源的结果或目标的目标。
	 * 
	 * 5）工作流程。序列的组成和顺序关系，可以安排在形成的时间和条件（非时间）行动计划（例如，护理计划，关键路径，临床试验协议，戒毒协议）。
	 * 有一个组法和ActRelationship都允许可执行的行动计划的详细规范的“属性的工作流控制套件”属性。这些属性
	 * 
	 * Act.repeatNumber
	 * 
	 * Act.interrubtibleInd
	 * 
	 * ActRelationship.sequenceNumber
	 * 
	 * ActRelationship.pauseQuantity
	 * 
	 * ActRelationship.checkpointCode
	 * 
	 * ActRelationship.splitCode
	 * 
	 * ActRelationship.joinCode
	 * 
	 * ActRelationship.sequenceNumber安排一个序列或并发的组件集合，表示逻辑分支以及并行任务（任务同时进行）法“的组成部分。
	 * 该ActRelationship归功于splitCode和并行joinCode分行选择如何控制或可执行文件。
	 * 
	 * Act.activityTime和ActRelationship.pauseQuantity允许一个明确的时间了一项行动计划。
	 * Act.repeatNumber允许指定的行为重复（循环），而Act.interruptibleInd决定是否可以通过一项法令，有关行为中断。
	 * 
	 * 有前提的ActRelationship类型，允许计划的步骤是有条件的，以前的操作状态或结果。该ActRelationship.
	 * checkpointCode规定的行为的先决条件时，在控制流测试。更多信息，请参阅在这个模型中的个别属性的条目。
	 * 
	 * 的的组成ActRelationship允许这些要在巢和层组织结构，以充分支持工作流管理。此筑巢和设计的工作流控制属性比喻与支持并发块结构化编程语言
	 * （叉，加入中断），并没有“转到”语句。所有工作流程的计划是建立在一复合行为（块）与结构化编程的原则一致通过测序组件（步骤）。
	 * 
	 * 6）主机功能关系的支持，事业，派生等广义的概念下，包括“针对性。”
	 * 
	 * 
	 * OpenIssue:
	 * 
	 * The property "isDocumentCharacteristic" is currently assigned to selected
	 * codes in ActRelationshipType, and is populated based on expected
	 * behaviour around negation. However, the values seem inappropriate when
	 * considering document behaviour. This property needs further analysis to
	 * determine whether a single property can suffice for both the negation and
	 * document characteristic use cases.
	 * 
	 * 属性“isDocumentCharacteristic”目前分配选择代码ActRelationshipType，填充的基础上否定周围的预期行为。
	 * 然而，价值观似乎考虑文件的行为时，不恰当的。这个属性需要进一步分析，以确定一个单一的财产是否足以否定和文件特性使用情况。
	 */
	private CS typeCode;
	/**
	 * Definition: An indicator specifying that the ActRelationship.typeCode
	 * should be interpreted as if the roles of the source and target Acts were
	 * reversed.
	 * 
	 * 指定一个指标，应作为解释，如果源和目标行为的角色ActRelationship.typeCode逆转。
	 * 
	 * 
	 * DesignComments:
	 * 
	 * Define Default annotation. Clarify why an indicator would be preferable
	 * to swapping source and target.
	 * 
	 * 定义预设批注。解释，为什么一个指标将是可取的交换源和目标。
	 */
	private BL inversionInd;
	/**
	 * Definition: Identifies the type(s) of ActRelationships that are not
	 * permitted to conduct across this ActRelationship.
	 * 
	 * 标识，不允许进行跨越这ActRelationship ActRelationships类型（S）。
	 * 
	 * 
	 * UsageConstraint:
	 * 
	 * This attribute can only be used if the serializable model in which it
	 * appears has a contextConductionStyle property of "V (vocabulary-based)".
	 * 
	 * 这个属性只能用于如果序列化的模型，它有contextConductionStyle财产的“V（词汇）”。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * If one or more codes are specified, all other ActRelationships with
	 * typeCodes that match one of the specified codes or that are
	 * specializations of one of the specified codes will not conduct. All other
	 * ActRelationships with typeCodes having a "conductible" property of "true"
	 * or whose ancestor has a "conductible" property of "true" will conduct.
	 * Conducted ActRelationships behave such that the Act being navigated to is
	 * treated as though it had the same association(s) as the Act being
	 * navigated from. Refer to the Core Principles specification for more
	 * information.
	 * 
	 * 如果指定了一个或多个代码，匹配一个指定的代码或typeCodes所有其他ActRelationships，是一个指定的代码不会进行专业。
	 * typeCodes所有其他ActRelationships
	 * ，有一个“导水”的“真”或他们的祖先有一个“导水”的“真”将进行财产的财产。虽然有相同协会
	 * （S）的航行，从法，该法案被视为航行进行ActRelationships的行为。请参阅更多信息，规范的核心原则。
	 */
	private DSET<CS> blockedContextActRelationshipType;
	/**
	 * Definition: Identifies the type(s) of Participations that are not
	 * permitted to conduct across this ActRelationship.
	 * 
	 * 标识，不允许进行跨越这ActRelationship参与型（S）。
	 * 
	 * 
	 * UsageConstraint:
	 * 
	 * This attribute can only be used if the serializable model in which it
	 * appears has a contextConductionStyle property of "V (vocabulary-based)".
	 * 
	 * 这个属性只能用于如果序列化的模型，它有contextConductionStyle财产的“V（词汇）”。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * If one or more codes are specified, all other Participations with
	 * typeCodes that match one of the specified codes or that are
	 * specializations of one of the specified codes will not conduct. All other
	 * Participations with typeCodes having a "conductible" property of "true"
	 * or whose ancestor has a "conductible" property of "true" will conduct.
	 * Conducted Participations behave such that the Act being navigated to is
	 * treated as though it had the same association(s) as the Act being
	 * navigated from. Refer to the Core Principles specification for more
	 * information.
	 * 
	 * 如果指定了一个或多个代码，与typeCodes匹配一个指定的代码，或所有其他参与是一个指定的代码不会进行专业。所有其他参与typeCodes有一个
	 * “导水”的“真”或他们的祖先有一个“导水”的“真”将进行财产的财产。进行参股行为虽然有同一协会（S）的航行，从法，该法案被视为航行。请参阅更多信息
	 * ，规范的核心原则。
	 */
	private DSET<CS> blockedContextParticipationType;
	/**
	 * Definition: Blocks conduction of act attribute values across this act
	 * relationship when true.
	 * 
	 * 通过这种行为关系的行为属性值时真正块传导。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * If true act attribute values are not conducted across this act
	 * relationship. If false the values of Act attributes having a
	 * "conductible" property of "true" will conduct. Conducted Act attribute
	 * values are treated as propagating and overriding.
	 * 
	 * 如果真正的行为属性值都没有进行过这种行为的关系。如果为假法“导水”的“真”的属性的属性值将进行。进行法属性值被视为传播和覆盖。
	 */
	private BN actAttributeContextBlockedInd;
	/**
	 * Deprecation Information: This attribute is deprecated from further use
	 * for RIM versions later than version 2.30. This attribute and those that
	 * worked with it have been superseded by the attributes
	 * ActRelationship.blockedContextActRelationshipType and
	 * ActRelationship.blockedContextParticipationType, together with the
	 * "conductible" property on concepts in the ActRelationshipType and
	 * ParticipationType code systems.
	 * 
	 * 此属性从RIM的版本进一步利用废弃后比2.30版本。此属性和那些与它的工作已被取代的的属性ActRelationship.
	 * blockedContextActRelationshipType和ActRelationship
	 * .blockedContextParticipationType
	 * ，连同“导水”的概念，在ActRelationshipType和ParticipationType代码系统属性。
	 * 
	 * 
	 * Definition: The manner in which this ActRelationship contributes to the
	 * context of the current Act, and whether it may be propagated to
	 * descendent Acts whose association allows such propagation (see
	 * ActRelationship.contextConductionInd).
	 * 
	 * 在这个ActRelationship贡献目前法案的背景下，是否可以传递给后代的行为，其协会允许这种传播（见ActRelationship.
	 * contextConductionInd）的方式。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * This attribute allows the clear specification of whether an association
	 * adds to the context associated with a particular item (e.g. adding an
	 * additional author) or whether it overrides and replaces the contextual
	 * assertion made by an Act relationship (e.g., identifying a sole author,
	 * independent of the containing item). It also indicates whether the
	 * association applies to only the immediate target act (non-propagating) or
	 * to derived acts as well (propagating).
	 * 
	 * This attribute works in concert with
	 * ActRelationship.contextConductionInd, which determines whether
	 * information will actually be conducted to a child Act, whatever the
	 * manner of conduction indicated by the contextControlCode.
	 * 
	 * If no value or default is specified for this attribute (i.e., it is
	 * null), no inference can be made about context. Systems must make their
	 * own assumptions on the basis of the data represented. For this reason,
	 * HL7 committees are encouraged to specify a default or fixed value for
	 * this attribute as part of their designs to ensure consistency of
	 * interpretation.
	 * 
	 * 这个属性允许的明确的规范，是否会增加相关的上下文与一个特定的项目（例如，增加一个额外的作者），或是否覆盖和替换法“的关系（例如，确定一个唯一作者，
	 * 独立的上下文断言含项目）。它还表示，该协会是否适用于只顾眼前的目标行为（非蔓延）或派生行为（传播）。
	 * 
	 * 此属性与ActRelationship.contextConductionInd，这就决定了信息是否会真正进行儿童法“，
	 * 无论传导方式由contextControlCode表示演唱会。
	 * 
	 * 如果没有值或默认指定此属性（即，它是空），没有推理，可以作出有关背景。表示的数据的基础上，系统必须使自己的假设。出于这个原因，
	 * HL7委员会鼓励指定该属性的默认值或固定值作为其设计的一部分，以确保解释的一致性。
	 * 
	 * 
	 * Rationale:
	 * 
	 * Humans often rely on context when interpreting information. For example,
	 * when reading a report taken from a folder containing a patient's medical
	 * record, the reader will infer that the report deals with the patient,
	 * even if there is no direct reference to the patient on the form. However,
	 * other pieces of information, such as the author of the folder (the
	 * hospital that maintains it) may sometimes apply to the contents of the
	 * folder (e.g., a report generated by a doctor at the hospital) and other
	 * times not (e.g., a copy of a report from another institution). Humans are
	 * quite good at making the necessary inferences about what context should
	 * be propagated from an item to something within that item. However,
	 * incorrect inferences can occur (perhaps the report in the patient's
	 * record deals with a relative). Furthermore, computers have substantially
	 * more difficulty making such inferences, even though they can be essential
	 * for decision-support systems.
	 * 
	 * 人类往往依赖于上下文时解释信息。例如，读者阅读时采取从文件夹中包含一个病人的医疗纪录的一份报告，将推断，该报告涉及的病人，
	 * 即使是没有直接引用窗体上的病人
	 * 。然而，其他部分的信息，如作者的文件夹（保持医院），有时会适用于该文件夹的内容（例如，由医生在医院产生的报告）和其他时间
	 * （例如，从另一个机构的报告的副本
	 * ）。人类是在什么情况下应传播从一个项目，该项目内的东西，必要的推论相当好。然而，不正确的推论可以发生（也许是一个相对的
	 * ，在病人的纪录交易报告）。此外，电脑有更多的困难作出这样的推论，即使他们可以是必不可少的决策支持系统。
	 * 
	 * 
	 * DesignComments:
	 * 
	 * In the example, it seems the dispense event would carry the author from
	 * the composite order.
	 * 
	 * 在这个例子中，似乎事件将进行笔者从复合材料的顺序分配。
	 * 
	 * 
	 * Examples:
	 * 
	 * An observation event has a patient participation marked
	 * "additive, propagating" (AP) and has component observation events linked
	 * through act relationships that are marked propagating. This means that
	 * the patient participation behaves as a patient participation of those
	 * component observation events in addition to the parent observation event.
	 * 
	 * A composite order (1) is created containing a pharmacy order (2) as well
	 * as requests for several lab tests (3). The composite order has
	 * participations for patient (4) and author (5), and an act relationship to
	 * a diagnosis (6), all marked as "additive, propagating." The "component"
	 * association (7) between the composite order (1) and the pharmacy order
	 * (2) is marked as conductive (contextConductionInd is True). The pharmacy
	 * order has an author participation (8) marked as
	 * "additive, non-propagating" (AN), and a reason relationship (9) to a
	 * diagnosis, marked as "overriding, propagating" (OP). The pharmacy order
	 * (2) further has a relationship to a dispense event (10), marked as
	 * conductive, and an association (11) to a drug protocol marked as
	 * non-conductive (contextConductionInd is False). The meaning would be as
	 * follows:
	 * 
	 * The pharmacy order (2) is interpreted as having the patient (4) from the
	 * composite order (1), and having two authors (the one from the composite
	 * order, and the one on the pharmacy order itself). The diagnosis for the
	 * pharmacy order relationship (9) would be the only diagnosis specified on
	 * the pharmacy order (2), not the one specified on the composite order (6).
	 * The dispense event (10) would carry the patient from the composite order
	 * (4) and the diagnosis from the pharmacy order (9), but no author. The
	 * drug protocol (11) would not be associated with a patient, diagnosis or
	 * author.
	 * 
	 * 观察事件有标有“添加剂，传播”（AP）的病人参与，有分量的观测活动，通过标志着传播行为的关系联系在一起。这意味着，
	 * 病人参与病人参与了这些组件观察事件除了父观测事件的行为。
	 * 
	 * 复合顺序（1）创建一个包含药店订单（2）以及一些实验室测试（3）请求。复合材料的顺序有患者参与（4）和作者（5），诊断和行为的关系（6），
	 * 所有标记为“添加剂，传播”。
	 * “组件”协会之间的复合命令（1）和药店的订单（2）（7）标记作为导电（contextConductionInd是真实的
	 * ）。药店为了有一个作家的参与（
	 * 8）标记为“添加剂，不传播”（AN）和理性的关系（9）诊断，“覆盖，传播”（OP）的标记。药店的订单（2）进一步有1免除事件
	 * （10），标记为导电的关系和关联（11）药物协议标志着作为非导电（contextConductionInd为False）。会的意义如下：
	 * 
	 * 药店的订单（2）被解释为从复合顺序（1）（4）病人中，有两位作者（一个从复合材料的顺序，药店为了自身）。药店顺序关系（9）的诊断会指定药店订单（2
	 * ），而不是对复合材料的顺序（6）指定一个唯一的诊断。免除事件（10）将进行复合顺序（4）和从药店顺序（9）的诊断病人，但没有作者。药物的协议（11
	 * ）将不会与一个病人，诊断或作者。
	 */
	private CS contextControlCode;
	/**
	 * Deprecation Information: This attribute is deprecated from further use
	 * for RIM versions later than version 2.30. This attribute and those that
	 * worked with it have been superseded by the attributes
	 * ActRelationship.blockedContextActRelationshipType and
	 * ActRelationship.blockedContextParticipationType, together with the
	 * "conductible" property on concepts in the ActRelationshipType and
	 * ParticipationType code systems.
	 * 
	 * 此属性从RIM的版本进一步利用废弃后比2.30版本。此属性和那些与它的工作已被取代的的属性ActRelationship.
	 * blockedContextActRelationshipType和ActRelationship
	 * .blockedContextParticipationType
	 * ，连同“导水”的概念，在ActRelationshipType和ParticipationType代码系统属性。
	 * 
	 * 
	 * Definition: An indicator determining whether associations in the parent
	 * act are to be conducted across the ActRelationship to the child act.
	 * 
	 * 一个指标决定是否在父行为协会整个ActRelationship的孩子的行为进行。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * Refer to ActRelationship.contextControlCode for rationale and examples.
	 * 
	 * 参阅ActRelationship.contextControlCode的理由和例子。
	 */
	private BL contextConductionInd;
	/**
	 * Definition: An integer specifying the relative sequential ordering of
	 * this relationship among other like-types relationships having the same
	 * source Act.
	 * 
	 * 一个整数，指定的相对顺序排列，喜欢其他类型具有相同的源法“的关系，这之间的关系。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * This attribute is part of the workflow control suite of attributes. An
	 * action plan is a composite Act with component Acts. In a sequential plan,
	 * each component has a sequenceNumber that specifies the ordering of the
	 * plan steps. Multiple components with the same sequenceNumber make a
	 * branch. Branches can be exclusive (case-switch) or can indicate parallel
	 * processes indicated by the splitCode.
	 * 
	 * If value is null, the relative position of the target Act is unspecified.
	 * (i.e., it may occur anywhere.)
	 * 
	 * Use the 'priorityNumber' attribute to indicate relative preference
	 * instead of order of occurrence.
	 * 
	 * 此属性是属性的流程控制套件的一部分。一项行动计划，是一个复合组件行为法“。在一个连续的计划，
	 * 每个组件都有一个指定的计划步骤的顺序的SequenceNumber
	 * 。具有相同的SequenceNumber多个组件构成的一个分支。分行可以独占（个案开关）或可以表明，splitCode表示的并行进程。
	 * 
	 * 如果值是空的，目标法的相对位置是不确定的。 （即，它可能发生在任何地方。）
	 * 
	 * 使用的“priorityNumber属性表示相对偏好，而不是为了发生。
	 */
	private INT_NONNEG sequenceNumber;
	/**
	 * Definition: An integer specifying the relative preference for considering
	 * this relationship before other like-typed relationships having the same
	 * source Act. Relationships with lower priorityNumber values are considered
	 * before and above those with higher values.
	 * 
	 * 一个整数，指定的相对优先考虑此之前，其他类似类型的关系，具有相同的源法的关系。较低priorityNumber值的关系被认为是前及以上更高的价值。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * For multiple criteria, this attribute specifies which criteria are
	 * considered before others. For components with the same sequence number,
	 * it specifies which ones are considered before others. Among alternatives
	 * or options that are being chosen by humans, the priorityNumber specifies
	 * preference.
	 * 
	 * The ordering may be a total ordering, in which all priority numbers are
	 * unique, or a partial ordering, in which the same priority may be assigned
	 * to more than one relationship.
	 * 
	 * 对于多个标准，这个属性指定该标准被认为是在别人面前。对于具有相同的序列号的组件，它指定哪些是认为在别人面前。之间的替代品或正在被人类的选择，
	 * priorityNumber指定偏好。
	 * 
	 * 订货会的总排序，在所有优先号码是独一无二的，或偏序，在相同的优先级可能被分配到多个关系。
	 */
	private REAL priorityNumber;
	/**
	 * Definition: A quantity of time that elapses or should elapse between the
	 * source act and the target act.
	 * 
	 * 一个时间量，逝去应相隔来源的行为和目标的行为。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * This attribute is part of the workflow control suite of attributes. An
	 * action plan is a composite Act with component Acts. In a sequential plan,
	 * each component has a sequenceNumber that specifies the ordering of the
	 * plan steps. Before any step with preconditions is executed, these
	 * conditions are tested: if the test is positive, the Act has clearance for
	 * execution. At that time, if the act has a pauseQuantity, the
	 * pauseQuantity timer is started: the Act is executed after the
	 * pauseQuantity has elapsed.
	 * 
	 * As a precondition (e.g., administer 3 hours prior to surgery), pause
	 * quantity is allowed to be negative, provided that it is possible to
	 * predict the occurrence of the target condition.
	 * 
	 * In general, pauseQuantity should only be specified when the source mood
	 * and target mood are identical, reflecting the time between the actual,
	 * intended or potential acts. However, in limited circumstances, it may
	 * also be used when the source act and target act have different moods. In
	 * this case, the source act must represent the realization of the target
	 * class. For example, event pointing to order, order pointing to proposal,
	 * etc.
	 * 
	 * The relationship type will generally be "fulfills" or "instantiates". In
	 * this case, the semantic indicates the difference in timing between the
	 * more realized source act and the more abstract target act. An alternative
	 * way of looking at it is that pauseQuantity represents the difference in
	 * time between two acts should the eventual event occur as specified in the
	 * act. For example: "The encounter started 30 minutes later than intended";
	 * or "The treatment began a week earlier than recommended".
	 * 
	 * 此属性是属性的流程控制套件的一部分。一项行动计划，是一个复合组件行为法“。在一个连续的计划，
	 * 每个组件都有一个指定的计划步骤的顺序的SequenceNumber
	 * 。任何先决条件的步骤执行之前，这些条件测试：如果测试是正面的，该法具有执行清拆。当时
	 * ，如果该行为具有pauseQuantity，pauseQuantity定时器启动：该法令执行后pauseQuantity已经过去了。
	 * 
	 * 作为一个先决条件（例如，管理在手术前3个小时），暂停数量可以是负面的，这是可能的预测目标情况的发生。
	 * 
	 * 在一般情况下，pauseQuantity应该只被指定源时的心情和目标的心情是相同的，反映了实际的，预期的或潜在的行为之间的时间。然而，
	 * 在有限的情况下，它也可能被用来当源的行为和目标的行为有不同的心情。在这种情况下，源行为必须代表目标类的实现。例如，指向事件指向订单，订单的建议等。
	 * 
	 * 一般的关系类型将是“符合”或“实例化”。在这种情况下，语义表示在时机更加意识到来源的行为和更抽象的目标行为之间的差异。看着它的另一种方法是，
	 * pauseQuantity代表在时间最终事件发生在该法规定两种行为之间的区别
	 * 。例如：“邂逅开始30分钟后，比预期”或“治疗一个星期前开始超过建议”。
	 * 
	 * 
	 * FormalConstraint:
	 * 
	 * Units SHALL be a type of time.
	 * 
	 * 单位应当是一个时间类型。
	 */
	private PQ_TIME pauseQuantity;
	/**
	 * Definition: The point in the course of an Act when a precondition for the
	 * Act is evaluated: e.g., before the Act starts for the first time, before
	 * every repetition, after each repetition but not before the first, or
	 * throughout the entire time of the Act.
	 * 
	 * 法“过程中的点时评估该法的一个先决条件是：如前法首次启动之前，每重复每次重复之后而不是之前的第一，或贯穿整个法的时间。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * This attribute is part of the workflow control suite of attributes. An
	 * action plan is a composite Act with component Acts. In a sequential plan,
	 * each component has a sequenceNumber that specifies the ordering of the
	 * plan steps. Before each step is executed, those with preconditions have
	 * their conditions tested; where the test is positive, the Act has
	 * clearance for execution. The checkpointCode specifies when the
	 * precondition is to be checked; it is analogous to the various conditional
	 * statements and loop constructs in programming languages "while-do" vs.
	 * "do-while" or "repeat-until" vs. "loop-exit."
	 * 
	 * For all checkpointCodes except "end," preconditions are being checked at
	 * the time when the preceding step of the plan has terminated and this step
	 * would be next in the sequence established by the sequenceNumber
	 * attribute.
	 * 
	 * When the checkpointCode for a criterion of a repeatable Act is "end," the
	 * criterion is tested only at the end of each repetition of that Act. When
	 * the condition holds true, the next repetition is ready for execution.
	 * 
	 * When the checkpointCode is "entry," the criterion is checked at the
	 * beginning of each repetition, if any, whereas "beginning" means the
	 * criterion is checked only once before the repetition "loop" starts.
	 * 
	 * The checkpointCode "through" is special in that it requires the condition
	 * to hold throughout the execution of the Act, even throughout a single
	 * execution. As soon as the condition turns false, the Act should receive
	 * an interrupt event (see Act.interruptibleInd) and will eventually
	 * terminate.
	 * 
	 * The checkpointCode "exit" is only used on a special plan step that
	 * represents a loop exit step. This allows an action plan to exit due to a
	 * condition tested inside the execution of this plan. Such exit criteria
	 * are sequenced with the other plan components using the
	 * ActRelationship.sequenceNumber.
	 * 
	 * 此属性是属性的流程控制套件的一部分。一项行动计划，是一个复合组件行为法“。在一个连续的计划，
	 * 每个组件都有一个指定的计划步骤的顺序的SequenceNumber
	 * 。执行每一步之前，先决条件的条件下进行测试;测试是积极的，该法具有执行清拆。前提是要检查时该checkpointCode规定
	 * ，它是类似于编程语言中的各种条件语句和循环结构“，而做”与“做，而”或“重复，直到”与“循环退出。 “
	 * 
	 * 对于除“末，”先决条件正在检查时，前面的步骤计划已终止时间，
	 * 这一步将在明年成立由的SequenceNumber属性的序列checkpointCodes。
	 * 
	 * 当checkpointCode一个可重复法的标准是“末，”标准只在每个重复该法案最终测试。当条件成立，未来的重复执行。
	 * 
	 * 当的checkpointCode是“项，”标准进行检查，如果有的话，在每次重复的开始，而“开始”意味着只有一次重复“循环”开始之前检查标准。
	 * 
	 * checkpointCode“通过”，是特殊的，它需要的条件，以保持整个一个执行该法的执行，甚至整个。尽快条件变成虚假的，
	 * 该法案应该会收到一个中断事件（见Act.interruptibleInd），并最终将终止。
	 * 
	 * “退出”checkpointCode仅用于在一个特殊的计划步骤，代表一个循环的退出步骤。这使得一项行动计划，退出由于内执行该计划的测试条件。
	 * 测序与其他计划使用ActRelationship.sequenceNumber组件等出口标准。
	 */
	private CS checkpointCode;
	/**
	 * Definition: The manner in which branches in an action plan are selected
	 * from among other branches.
	 * 
	 * 分支机构在一项行动计划，以何种方式从其他分支机构之间的选择。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * This attribute is part of the workflow control suite of attributes. An
	 * action plan is a composite Act with component Acts. In a sequential plan,
	 * each component has a sequenceNumber that specifies the ordering of the
	 * plan steps. Branches exist when multiple components have the same
	 * sequenceNumber. The splitCode specifies whether a branch is executed
	 * exclusively (case-switch) or inclusively, i.e., in parallel with other
	 * branches.
	 * 
	 * In addition to exclusive and inclusive split the splitCode specifies how
	 * the pre-condition (also known as "guard conditions" on the branch) are
	 * evaluated. A "try once" guard condition may be evaluated once when the
	 * branching step is entered and if the conditions do not hold at that time,
	 * the branch is abandoned. Conversely, execution of a "wait" branch may
	 * wait until the guard condition turns true.
	 * 
	 * In exclusive wait branches, the first branch whose guard conditions turn
	 * true will be executed and all other branches abandoned. In inclusive wait
	 * branches some branches may already be executed while other branches still
	 * wait for their guard conditions to turn true.
	 * 
	 * 此属性是属性的流程控制套件的一部分。一项行动计划，是一个复合组件行为法“。在一个连续的计划，
	 * 每个组件都有一个指定的计划步骤的顺序的SequenceNumber。分行存在多个组件时，有相同的SequenceNumber。
	 * splitCode指定是否只执行一个分支（个案开关）或（含），即在与其他分支并行。
	 * 
	 * 除了以独家性和包容性的分裂splitCode指定的先决条件（又称在树枝上的“后卫”）进行评估。一个“再试一次”警戒条件时，
	 * 可以计算一次的分支步骤进入，当时如果条件不成立，被遗弃的分支。相反，“等待”分支的执行可能会等到警卫条件变成真。
	 * 
	 * 在独家等待分行，第一家分行，其警戒条件变成真会被执行，并放弃所有其他分支。在包容等待分支机构，有些分支机构可能已经被执行，
	 * 而其他分支仍然等待他们的警戒条件，把真实的。
	 * 
	 * 
	 * Examples:
	 * 
	 * Exclusive wait, inclusive wait, exclusive try once.
	 * 
	 * 专属的等待，等待，包容性的独家再试一次。
	 */
	private CS splitCode;
	/**
	 * Definition: The manner in which concurrent Acts are resynchronized in a
	 * parallel branch construct.
	 * 
	 * 在并行分支重新同步并发行为方式。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * This attribute is part of the workflow control suite of attributes. An
	 * action plan is a composite Act with component Acts. In a sequential plan,
	 * each component has a sequenceNumber that specifies the ordering of the
	 * plan steps. Branches exist when multiple components have the same
	 * sequenceNumber. Branches are parallel if the splitCode specifies that
	 * more than one branch can be executed at the same time. The joinCode then
	 * specifies if and how the branches are resynchronized.
	 * 
	 * The principal re-synchronization actions are (1) the control flow waits
	 * for a branch to terminate (wait-branch), (2) the branch that is not yet
	 * terminated is aborted (kill-branch), (3) the branch is not
	 * re-synchronized at all and continues in parallel (detached branch).
	 * 
	 * A kill-branch is only executed if there is at least one active wait
	 * branch. If there is no other wait branch active, a kill-branch is not
	 * started at all (rather than being aborted shortly after it is started).
	 * Since a detached branch is unrelated to all other branches, active
	 * detached branches do not prevent a kill-branch from being aborted.
	 * 
	 * 此属性是属性的流程控制套件的一部分。一项行动计划，是一个复合组件行为法“。在一个连续的计划，
	 * 每个组件都有一个指定的计划步骤的顺序的SequenceNumber
	 * 。分行存在多个组件时，有相同的SequenceNumber。分行是平行的，如果splitCode指定可以在同一时间执行多个分支。
	 * joinCode然后指定是否以及如何重新同步分行。
	 * 
	 * 重新同步的主要行动是：（1）控制流等待一个分支，终止（观望分行），（2）尚未终止的分支中止（杀死分支），（3）分支重新同步平行（独立分支）。
	 * 
	 * 如果有至少有一个积极的等待分公司，分公司只执行一个kill。如果有任何其他等待分行积极，杀分支未启动（而不是被中止后不久开始）。由于独立的分支，
	 * 是所有其他部门无关，不活跃的独立分支防止被中止一个kill分支。
	 * 
	 * 
	 * Examples:
	 * 
	 * Detached, kill, exclusive wait.
	 * 
	 * 独立，杀，的独家等待。
	 */
	private CS joinCode;
	/**
	 * Definition: An indicator that asserts that the meaning of the link is
	 * negated.
	 * 
	 * 一个指标，声称该链接的含义是否定的。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * This attribute is used primarily for clarifying statements. As the
	 * examples show, the use of this attribute is quite limited, notably
	 * contrast this with the Act.negationInd that actually requires that the
	 * described Act not exist, not be done, etc. whereas the
	 * ActRelationship.negationInd merely negates this relationship between
	 * source and target act, but does not change the meaning of each Act.
	 * 
	 * Note also the difference between negation and the contrary. A
	 * contraindication is the contrary of an indication (reason) but not the
	 * negation of the reason. The fact that lower back pain is not a reason to
	 * prescribe antibiotics doesn't mean that antibiotics are contraindicated
	 * with lower back pain.
	 * 
	 * 此属性主要用于澄清声明。的例子表明，使用该属性是相当有限的，尤其是对比度与实际需要的Act.negationInd描述法，不存在这个，不能做等，
	 * 而ActRelationship.negationInd只是否定这个源和之间的关系目标的行为，但不改变各法的意义。
	 * 
	 * 还要注意的否定，相反之间的差异。禁忌是相反的指示（原因），但不能否定的原因。事实上，腰痛是不开抗生素的理由并不意味着抗生素腰痛禁忌。
	 * 
	 * 
	 * Examples:
	 * 
	 * If the relationship without negation specifies that Act A has Act B as a
	 * component, then the negation indicator specifies that Act A does not have
	 * Act B as a component. If B is a reason for A, then negation means that B
	 * is not a reason for A. If B is a pre-condition for A, then negation means
	 * that B is not a precondition for A.
	 * 
	 * 如果没有否定的关系，指定该法有乙法“作为一个组件，然后否定指标指定该法A不法案乙作为一个组件。如果B是一个原因，则否定了B不是答的原因，
	 * 如果B是一个先决条件，为A，则否定意味着B是不是对A的一个先决条件
	 */
	private BL negationInd;
	/**
	 * Definition: The logical conjunction of the criteria among all the
	 * condition-links of Acts (e.g., and, or, exlusive-or).
	 * 
	 * 之间的所有条件的行为，链接（如，或EXLUSIVE或）标准的逻辑结合。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * This attribute is used for criteria, typically in definition or goal
	 * mood.
	 * 
	 * Upon evaluation, the criterion is passed if all "and" criteria are true.
	 * If "or" and "and" criteria occur together, one criterion out of the
	 * "or"-group must be true and all "and" criteria must be true also. If
	 * "xor" criteria occur together with "or" and "and" criteria, exactly one
	 * of the "xor" criteria must be true, and at least one of the "or" criteria
	 * and all "and" criteria must be true. In other words, the sets of "and",
	 * "or", and "xor" criteria are in turn combined by a logical "and" operator
	 * (all "and" criteria and at least one "or" criterion and exactly one "xor"
	 * criterion). To overcome this ordering, Act criteria can be nested as
	 * necessary.
	 * 
	 * 这个属性是用来为标准，通常在定义或目标的心情。
	 * 
	 * 经评估，标准传递，如果所有“和”标准是真实的。必须是真实的，所有如果“或”和“和”标准发生一起，一个标准“或”组“和”标准也必须是真实的。如果出现
	 * “异”的准则“或”和“和”标准，完全的“异”的标准之一必须是真实的，和至少一个“或”标准和所有“和”标准，必须是真实的。换句话说，集“和”“或”，
	 * “异”的准则是在左转的逻辑“和”运算符（所有“和”标准，并至少有一个“或”标准只有一个“XOR结合“标准）。为了克服这个顺序，
	 * 法准则可以嵌套是必要的。
	 */
	private CS conjunctionCode;
	/**
	 * Definition: A character string name for the input parameter from which
	 * the source Act of this ActRelationship derives some of its attributes.
	 * The local variable name is bound in the scope of the Act.derivationExpr
	 * with its value being an Act selected based on the input parameter
	 * specified by this attribute.
	 * 
	 * 一个字符串输入参数名称本ActRelationship的源法源于它的一些属性。局部变量的名称约束，
	 * 其值这个属性所指定的输入参数的基础上选择了一项法令，中的Act.derivationExpr范围。
	 */
	private ST_SIMPLE localVariableName;
	/**
	 * Definition: An indication that the source Act is intended to be
	 * interpreted independently of the target Act.
	 * 
	 * 源法“的目的来解释独立的目标法”的指示。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * The indicator cannot prevent an individual or application from separating
	 * the Acts, but indicates the author's desire and willingness to attest to
	 * the content of the source Act if separated from the target Act. Note that
	 * this attribute is orthogonal and unrelated to the RIM's
	 * context/inheritance mechanism. If the context of an Act is propagated to
	 * nested Acts, it is assumed that those nested Acts are not intended to be
	 * interpreted without the propagated context.
	 * 
	 * 该指标不能防止个人或应用程序分离行为，但表示作者的愿望，并愿意证明源法“的内容，如果目标法分离。请注意，此属性是正交和RIM的上下文/继承机制无关
	 * 。如果法的过程中传播到嵌套的行为，它是假设这些嵌套行为的目的，并不是没有传播背景下解释。
	 */
	private BL seperatableInd;
	/**
	 * Definition: An indication that the target of the relationship will be a
	 * filtered subset of the total related set of targets.
	 * 
	 * 迹象显示该目标的关系将是一个总目标的一组相关的过滤子集。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * This attribute is used when there is a need to limit the number of
	 * components to the first, the last, the next, the total, the average or
	 * some other filtered or calculated subset.
	 * 
	 * 使用此属性时，有必要限制的部件数量第一，过去，未来，总的平均或其他一些过滤或计算子集。
	 * 
	 * 
	 * Examples:
	 * 
	 * First, maximum, summary.
	 * 
	 * 首先，最大，总结。
	 */
	private CS subsetCode;
	/**
	 * Definition: An assertion that specific relationship between the source
	 * and target Acts is uncertain.
	 * 
	 * 源和目标行为之间的具体关系是不确定的断言。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * Uncertainty asserted using this attribute applies only to the
	 * relationship between two acts. The certainty of the acts themselves
	 * should be conveyed via Act.uncertaintyCode.
	 * 
	 * 不确定性断言，使用这个属性只适用于两种行为之间的关系。确定性的行为本身应转达通过Act.uncertaintyCode。
	 * 
	 * 
	 * Examples:
	 * 
	 * A particular exposure event is suspected but not known to have caused a
	 * particular symptom: stated with uncertainty.
	 * 
	 * 一个特定的曝光事件被怀疑，但不知道已经造成了特别的症状：不确定性的说明。
	 */
	private CD uncertaintyCode;

	@ManyToOne
	private Act target;
	@ManyToOne
	private Act source;

	public CS getTypeCode() {
		return typeCode;
	}

	public void setTypeCode(CS typeCode) {
		this.typeCode = typeCode;
	}

	public BL getInversionInd() {
		return inversionInd;
	}

	public void setInversionInd(BL inversionInd) {
		this.inversionInd = inversionInd;
	}

	public DSET<CS> getBlockedContextActRelationshipType() {
		return blockedContextActRelationshipType;
	}

	public void setBlockedContextActRelationshipType(
			DSET<CS> blockedContextActRelationshipType) {
		this.blockedContextActRelationshipType = blockedContextActRelationshipType;
	}

	public DSET<CS> getBlockedContextParticipationType() {
		return blockedContextParticipationType;
	}

	public void setBlockedContextParticipationType(
			DSET<CS> blockedContextParticipationType) {
		this.blockedContextParticipationType = blockedContextParticipationType;
	}

	public BN getActAttributeContextBlockedInd() {
		return actAttributeContextBlockedInd;
	}

	public void setActAttributeContextBlockedInd(
			BN actAttributeContextBlockedInd) {
		this.actAttributeContextBlockedInd = actAttributeContextBlockedInd;
	}

	public CS getContextControlCode() {
		return contextControlCode;
	}

	public void setContextControlCode(CS contextControlCode) {
		this.contextControlCode = contextControlCode;
	}

	public BL getContextConductionInd() {
		return contextConductionInd;
	}

	public void setContextConductionInd(BL contextConductionInd) {
		this.contextConductionInd = contextConductionInd;
	}

	public INT_NONNEG getSequenceNumber() {
		return sequenceNumber;
	}

	public void setSequenceNumber(INT_NONNEG sequenceNumber) {
		this.sequenceNumber = sequenceNumber;
	}

	public REAL getPriorityNumber() {
		return priorityNumber;
	}

	public void setPriorityNumber(REAL priorityNumber) {
		this.priorityNumber = priorityNumber;
	}

	public PQ_TIME getPauseQuantity() {
		return pauseQuantity;
	}

	public void setPauseQuantity(PQ_TIME pauseQuantity) {
		this.pauseQuantity = pauseQuantity;
	}

	public CS getCheckpointCode() {
		return checkpointCode;
	}

	public void setCheckpointCode(CS checkpointCode) {
		this.checkpointCode = checkpointCode;
	}

	public CS getSplitCode() {
		return splitCode;
	}

	public void setSplitCode(CS splitCode) {
		this.splitCode = splitCode;
	}

	public CS getJoinCode() {
		return joinCode;
	}

	public void setJoinCode(CS joinCode) {
		this.joinCode = joinCode;
	}

	public BL getNegationInd() {
		return negationInd;
	}

	public void setNegationInd(BL negationInd) {
		this.negationInd = negationInd;
	}

	public CS getConjunctionCode() {
		return conjunctionCode;
	}

	public void setConjunctionCode(CS conjunctionCode) {
		this.conjunctionCode = conjunctionCode;
	}

	public ST_SIMPLE getLocalVariableName() {
		return localVariableName;
	}

	public void setLocalVariableName(ST_SIMPLE localVariableName) {
		this.localVariableName = localVariableName;
	}

	public BL getSeperatableInd() {
		return seperatableInd;
	}

	public void setSeperatableInd(BL seperatableInd) {
		this.seperatableInd = seperatableInd;
	}

	public CS getSubsetCode() {
		return subsetCode;
	}

	public void setSubsetCode(CS subsetCode) {
		this.subsetCode = subsetCode;
	}

	public CD getUncertaintyCode() {
		return uncertaintyCode;
	}

	public void setUncertaintyCode(CD uncertaintyCode) {
		this.uncertaintyCode = uncertaintyCode;
	}

	public Act getTarget() {
		return target;
	}

	public void setTarget(Act target) {
		this.target = target;
	}

	public Act getSource() {
		return source;
	}

	public void setSource(Act source) {
		this.source = source;
	}

	public static long getSerialversionuid() {
		return serialVersionUID;
	}

}
